Creating data in a data store using a dynamic ontology

ABSTRACT

In one embodiment, a method comprises creating and storing an ontology for a data store in response to receiving first user input defining the ontology, wherein the ontology comprises a plurality of data object types and a plurality of object property types; creating one or more parser definitions in response to receiving second user input defining the parser definitions, wherein each of the parser definitions specifies one or more sub-definitions of how to transform first input data into modified input data that is compatible with one of the object property types; and storing each of the one or more parser definitions in association with one of the plurality of object property types.

BENEFIT CLAIM

This application claims benefit and priority under 35 U.S.C. §120 as a Continuation of U.S. patent application Ser. No. 11/602,626, filed Nov. 20, 2006, now U.S. Pat. No. 7,962,495 the entire contents of which is hereby incorporated by reference as if fully set forth herein. The applicant(s) hereby rescind any disclaimer of claim scope in the parent application(s) or the prosecution history thereof and advise the USPTO that the claims in this application may be broader than any claim in the parent application(s).

FIELD OF THE INVENTION

The present disclosure generally relates to techniques for creating data in a data store.

BACKGROUND

The approaches described in this section are approaches that could be pursued, but not necessarily approaches that have been previously conceived or pursued. Therefore, unless otherwise indicated, it should not be assumed that any of the approaches described in this section qualify as prior art merely by virtue of their inclusion in this section.

Computer-based database systems, such as relational database management systems, typically organize data according to a fixed structure of tables and relationships. The structure may be described using an ontology, embodied in a database schema, comprising a data model that is used to represent the structure and reason about objects in the structure.

An ontology of a database is normally fixed at the time that the database is created. Any change in the ontology represented by the schema is typically extremely disruptive to the database system and requires a database administrator to modify tables or relationships, or create new tables or relationships.

The rigidity of the typical database ontology is a serious drawback for organizations that require flexible and dynamic data processing techniques according to changes in the data that is collected. For example, intelligence analysis is poorly suited to conventional fixed ontology systems.

SUMMARY

In one embodiment, a method comprises creating and storing an ontology for a data store in response to receiving first user input defining the ontology, wherein the ontology comprises a plurality of data object types and a plurality of object property types; creating one or more parser definitions in response to receiving second user input defining the parser definitions, wherein each of the parser definitions specifies one or more sub-definitions of how to transform first input data into modified input data that is compatible with one of the object property types; storing each of the one or more parser definitions in association with one of the plurality of object property types; wherein the machine-executed operation is at least one of (a) sending said instructions over transmission media, (b) receiving said instructions over transmission media, (c) storing said instructions onto a machine-readable storage medium, and (d) executing the instructions.

In one feature, the method further comprises receiving the first input data; determining whether the first input data matches one of the parser sub-definitions; using a matching one of the parser sub-definitions, creating and storing the modified input data; storing the modified input data in a property of the property type that is identified in the matching one of the parser sub-definitions.

In another feature, creating and storing one or more parser definitions comprises creating and storing one or more program code modules, wherein each of the code modules comprises computer program code which when executed causes transforming the first input data into the modified input data.

In another feature, creating and storing one or more parser definitions comprises creating and storing one or more transformation expressions, wherein each of the transformation expressions comprises one or more syntactic patterns and a property type identifier associated with each of the syntactic patterns.

In yet another feature, creating and storing one or more parser definitions comprises creating and storing one or more transformation expressions, wherein each of the transformation expressions comprises one or more syntactic patterns and a property type identifier associated with each of the syntactic patterns, and the method further comprises receiving the first input data; determining whether the first input data matches one of the syntactic patterns; using a matching one of the syntactic patterns, creating and storing modified input data; storing the modified input data in a property of the property type that is identified by the property type identifier associated with the matching one of the syntactic patterns.

In still another feature, creating one or more parser definitions comprises creating one or more parser definitions comprising a constraint on what modified input data is acceptable for creation of a property of one of the object property types. In a further feature, creating one or more parser definitions comprises creating one or more parser definitions comprising a default value to substitute for one component of the modified input data.

In another feature, the method further comprises receiving the first input data; determining whether the first input data matches successive different ones of the parser sub-definitions until a matching parser sub-definition is identified; using a matching one of the parser sub-definitions, creating and storing the modified input data; storing the modified input data in a property of the property type that is identified in the matching one of the parser sub-definitions.

According to another embodiment, a data storage system comprises a data store; an ontology coupled to the data store and comprising a plurality of data object types and a plurality of object property types; a parser coupled to the ontology and configured to receive input data and transform the input data into modified data to store in a property of one of the property types according to one or more parser definitions; wherein each of the object property types comprises one or more of the parser definitions, wherein each of the parser definitions specifies one or more sub-definitions of how to transform first input data into modified input data that is compatible with one of the object property types.

According to another embodiment, an apparatus comprises means for creating and storing an ontology for a data store in response to receiving first user input defining the ontology, wherein the ontology comprises a plurality of data object types and a plurality of object property types; means for creating one or more parser definitions in response to receiving second user input defining the parser definitions, wherein each of the parser definitions specifies one or more sub-definitions of how to transform first input data into modified input data that is compatible with one of the object property types; and means for storing each of the one or more parser definitions in association with one of the plurality of object property types.

In another embodiment, a graphical user interface comprises an expression pattern field configured to accept user input specifying a transformation expression pattern that specifies how to transform first input data into modified input data; one or more parser sub-definitions each comprising: a portion of the transformation expression pattern; a combo box configured to accept user input specifying one of a plurality of object property component types of an ontology of a data store; wherein each of the parser sub-definitions specifies how to transform a portion of the first input data into a portion of modified input that can be stored in the specified component of one of the plurality of object property types.

In one feature, the one or more parser sub-definitions comprise a constraint on how to transform the portion of the first input data into the portion of modified input data that is compatible with one of the object property types. In yet another feature, the one or more parser sub-definitions comprise a default value to substitute for the modified input data if it is empty.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements and in which:

FIG. 1 illustrates a system for creating data in a data store using a dynamic ontology;

FIG. 2 illustrates defining a dynamic ontology for use in creating data in a data store;

FIG. 3 illustrates a method of transforming data and creating the data in a data store using a dynamic ontology;

FIG. 4 illustrates an example object type editor;

FIG. 5A illustrates an example parser editor;

FIG. 5B illustrates an example property editing wizard in which multiple parsers have been created for a particular property; and

FIG. 6 illustrates a computer system with which an embodiment may be implemented.

DESCRIPTION OF EXAMPLE EMBODIMENTS

In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, that the present invention may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the present invention. In an embodiment, a user of a database system specifies an ontology of the database in terms of object types and property types for properties of the objects. The user further specifies how to parse input data for the database and how to map the parsed data into database elements such as objects or object properties. The database is chosen as an example embodiment, other embodiments such as flat files or search indexes could be considered as well.

I. Dynamic Ontology Database System

FIG. 1 illustrates a system for creating data in a database using a dynamic ontology. A parser 102 is coupled to an ontology 106, which is coupled to a database 108. In an embodiment, ontology 106 comprises stored information providing a data model of data stored in database 108, and the ontology is defined by one or more object types 110 and one or more property types 116. One or more objects 112 in the database 108 may be instantiated based on the object types 110, and each of the objects has one or more properties 114A, 114B that are instantiated based on property types 116. The property types 116 each may comprise one or more components 118, such as a string, number, etc. Property types 116 may be instantiated based on a base type 120. For example, a base type 120 may be “Locations” and a property type 116 may be “Home.”

In an embodiment, a user of the system uses an object type editor 124 to create the object types 110 and define attributes of the object types. In an embodiment, a user of the system uses a property type editor 126 to create the property types 116 and define attributes of the property types.

In an embodiment, creating a property type 116 using the property type editor 126 involves defining at least one parser definition using a parser editor 122. A parser definition comprises metadata that informs parser 102 how to parse input data 100 to determine whether values in the input data can be assigned to the property type 116 that is associated with the parser definition. In an embodiment, each parser definition may comprise a regular expression parser 104A or a code module parser 104B. In other embodiments, other kinds of parser definitions may be provided using scripts or other programmatic elements. The elements of a regular expression parser 104A and a code module parser 104B are described further in subsequent sections. Once defined, both a regular expression parser 104A and a code module parser 104B can provide input to parser 102 to control parsing of input data 100.

In one embodiment of using the system of FIG. 1, input data 100 is provided to parser 102. An object-property mapping for the input data 100 enables the parser to determine which object type 110 should receive data from a row of the input data, and which property types 116 should receive data from individual field values in the input data. Based on the object-property mapping 101, the parser 102 selects one of the parser definitions that is associated with a property type in the input data. The parser parses an input data field using the selected parser definition, resulting in creating modified data 103. The modified data 103 is added to the database 108 according to ontology 106 by storing values of the modified data in a property of the specified property type. As a result, input data 100 having varying format or syntax can be created in database 108. The ontology 106 may be modified at any time using object type editor 124 and property type editor 126. Parser editor 122 enables creating multiple parser definitions that can successfully parse input data 100 having varying format or syntax and determine which property types should be used to transform input data 100 into modified input data 103.

II. Defining a Dynamic Ontology

FIG. 2 illustrates defining a dynamic ontology for use in creating data in a database. For purposes of illustrating a clear example, steps 202-209 of FIG. 2 are first described at a high level, and details of an example implementation follow the high level description.

In step 202, one or more object types are created for a database ontology. In step 206, one or more property types are created for each object type. As indicated in step 204, the attributes of object types or property types of the ontology may be edited or modified at any time.

In step 208, at least one parser definition is created for each property type. At step 209, attributes of a parser definition may be edited or modified at any time.

In an embodiment, each property type is declared to be representative of one or more object types. A property type is representative of an object type when the property type is intuitively associated with the object type. For example, a property type of “Social Security Number” may be representative of an object type “Person” but not representative of an object type “Business.”

In an embodiment, each property type has one or more components and a base type. In an embodiment, a property type may comprise a string, a date, a number, or a composite type consisting of two or more string, date, or number elements. Thus, property types are extensible and can represent complex data structures. Further, a parser definition can reference a component of a complex property type as a unit or token.

An example of a property having multiple components is a Name property having a Last Name component and a First Name component. An example of raw input data is “Smith, Jane”. An example parser definition specifies an association of input data to object property components as follows: {LAST_NAME}, { FIRST_NAME}→Name:Last, Name:First. In an embodiment, the association {LAST_NAME}, {FIRST_NAME} is defined in a parser definition using regular expression symbology. The association {LAST_NAME}, {FIRST_NAME} indicates that a last name string followed by a first name string comprises valid input data for a property of type Name. In contrast, input data of “Smith Jane” would not be valid for the specified parser definition, but a user could create a second parser definition that does match input data of “Smith Jane”. The definition Name:Last, Name:First specifies that matching input data values map to components named “Last” and “First” of the Name property.

As a result, parsing the input data using the parser definition results in assigning the value “Smith” to the Name:Last component of the Name property, and the value “Jane” to the Name:First component of the Name property.

In an embodiment, administrative users use an administrative editor to create or edit object types and property types. In an embodiment, users use the administrative editor to specify parser definitions and to associate regular expressions, code modules or scripts with the parser definitions. In the administrative editor, a user can specify attributes and components of a property type. For example, in one embodiment a user specifies a graphical user interface icon that is associated with the property type and displayed in a user interface for selecting the property type. The user further specifies a parser definition that is associated with the property type and that can parse input data and map the input data to properties corresponding to the property type. The user further specifies a display format for the property type indicating how users will see properties of that property type.

FIG. 4 illustrates an example object type editor. In an embodiment, an object type editor panel 402 comprises graphical buttons 404 for selecting add, delete, and edit functions, and one or more rows 406 that identify object types and a summary of selected attributes of the object types. Example selected attributes that can be displayed in object editor panel 402 include an object type name 408 (for example, “Business”), a uniform resource identifier (URI) 410 specifying a location of information defining the object type (for example, “com.palantir.object.business”), and a base type 412 of the object type, also expressed in URI format (for example, “com.palantir.object.entity”). Each URI also may include a graphical icon 414.

In an embodiment, a user interacts with a computer to perform the following steps to define an object type. Assume for purposes of an example that the new object type is Vehicle. Using the object type editor, the user selects the “Add Object Type” button 404 and the computer generates and displays a panel that prompts the user to enter values for a new object type. The user selects a base object type of Entity, which may comprise any person, place or thing. The user assigns a graphical icon to the Vehicle object type. The user assigns a display name of “Vehicle” to the object type.

In an embodiment, a user interacts with the computer to define a property type in a similar manner. The user specifies a name for the property type, a display name, and an icon. The user may specify one or more validators for a property type. Each validator may comprise a regular expression that input data modified by a parser must match to constitute valid data for that property type. In an embodiment, each validator is applied to input data before a process can store the modified input data in an object property of the associated property type. Validators are applied after parsing and before input data is allowed to be stored in an object property.

In various embodiments, validators may comprise regular expressions, a set of fixed values, or a code module. For example, a property type that is a number may have a validator comprising a regular expression that matches digits 0 to 9. As another example, a property type that is a US state may have a validator that comprises the set {AK, AL, CA . . . VA} of valid two-letter postal abbreviations for states. Validator sets may be extendible to allow a user to add further values. A property type may have component elements, and each component element may have a different validator. For example, a property type of “Address” may comprise as components “City”, “State”, and “ZIP”, each of which may have a different validator.

In an embodiment, defining a property type includes identifying one or more associated words for the property type. The associated words support search functions in large database systems. For example, a property type of “Address” may have an associated word of “home” so that a search in the system for “home” properties will yield “Address” as one result.

In an embodiment, defining a property type includes identifying a display formatter for the property type. A display formatter specifies how to print or display a property type value.

In an embodiment, the parser definitions each include a regular expression that matches valid input, and the parser uses a regular expression processing module. For example, conventional Java language processors typically have regular expression processing modules built in. In an embodiment, parser definitions comprising regular expressions may be chained together. In another embodiment, one or more of the parser definitions each include a code module that contains logic for parsing input data and determining whether the input data matches a specified syntax or data model. The code module may be written in Java, JavaScript, or any other suitable source language.

In an embodiment, there may be any number of parser definitions and sub-definitions. The number of parser definitions is unimportant because the input data is applied successively to each parser definition until a match occurs. When a match occurs, the input data is mapped using the parser sub definitions to one or more components of an instance of an object property. As a result, input data can vary syntactically from a desired syntax but correct data values are mapped into correct object property values in a database.

Accordingly, referring again to FIG. 2, creating a parser definition for a property type at step 208 may comprise selecting a parser type such as a regular expression, code module, or other parser type. When the parser type is “code module,” then a user specifies the name of a particular code module, script, or other functional element that can perform parsing for the associated property type.

In an embodiment, defining a property type includes creating a definition of a parser for the property type using a parser editor. FIG. 5A illustrates an example parser editor user interface screen display. In an embodiment, screen display 502 comprises a Parser Type combo box 504 that can receive a user selection of a parser type, such as “Regular Expression” or “Code Module.” Screen display 502 further comprises a Name text entry box 506 that can receive a user-specified name for the parser definition.

When the parser type is “regular expression,” steps 214-220 are performed. At step 214, regular expression text is specified. For example, when the Parser Type value of combo box 504 is “Regular Expression,” screen display 502 comprises an Expression Pattern text box 508 that can receive a user entry of regular expression pattern text.

In step 216, a property type component and a matching sub-definition of regular expression text is specified. For example, screen display 502 further comprises one or more property type component mappings 510. Each property type component mapping associates a sub-definition of the regular expression pattern text with the property type component that is shown in a combo box 512. A user specifies a property type component by selecting a property type component using combo box 512 for an associated sub-definition 513. As shown in step 218, specifying a property type component and sub-definition of regular expression text may be repeated for all other property type components of a particular property type. As seen in the example of FIG. 5A, six (6) property type component mappings 510 have been created for different property types (ADDRESS1, ADDRESS2, ADDRESS3, CITY, STATE, ZIP).

In step 220, a user may specify one or more constraints, default values, and/or other attributes of a parser definition. In the example of FIG. 5A, the user also may specify that a match to a particular property type component is not required by checking a “Not Required” check box 514. Screen display 502 may further comprise a Default Value text box 514 that can receive user input for a default value for the property type component. If a Default Value is specified, then the associated property type receives that value if no match occurs for associated grouping of the regular expression. In alternative embodiments, other constraints may be specified.

At step 222, the parser definition is stored in association with a property type. For example, selecting the SAVE button 520 of FIG. 5A causes storing a parser definition based on the values entered in screen display 502. Parser definitions may be stored in database 108.

For purposes of illustrating a clear example, the approach of FIG. 2 has been described with reference to FIG. 5A. However, the approach of FIG. 2 may be implemented using other mechanisms for creating and specifying the values and elements identified in FIG. 2, and the particular GUI of FIG. 5A is not required.

III. Creating Data in a Database using a Dynamic Ontology

FIG. 3 illustrates a method of transforming data and creating the data in a database using a dynamic ontology. For purposes of illustrating a clear example, the approach of FIG. 3 is described herein with reference to FIG. 1. However, the approach of FIG. 3 may be implemented using other mechanisms for performing the functional steps of FIG. 3, and the particular system of FIG. 1 is not required.

In step 302, input data is received. In an embodiment, an input data file is received. The input data file may comprise a comma-separated value (CSV) file, a spreadsheet, XML or other input data file format. Input data 100 of FIG. 1 may represent such file formats or any other form of input data.

In step 304, an object type associated with input data rows of the input data is identified, and one or more property types associated with input data fields of the input data are identified. For example, the object-property mapping 101 of FIG. 1 specifies that input data 100 comprises rows corresponding to object type PERSON and fields corresponding to property type components LAST_NAME, FIRST_NAME of property type NAME. The object-property mapping 101 may be integrated into input data 100 or may be stored as metadata in association with a data input tool.

In step 306, a row of data is read from the input data, and one or more field values are identified based on delimiters or other field identifiers in the input data.

In step 308, a set of parser definitions associated with the property type of a particular input data field is selected. For example, metadata stored as part of creating a property type specifies a set of parser definitions, as previously described in connection with FIG. 5A.

In step 310, the next parser definition is applied to an input data field value. Thus, data fields are read from each row of the file and matched to each parser that has been defined for the corresponding property types. For example, assume that the mapping indicates that an input data CSV file comprises (Last Name, First Name) values for Name properties of Person objects. Data fields are read from the input data CSV file and compared to each of the parsers that has been defined for the Name property type given the First Name field and Last Name field. If a match occurs for a (Last Name, First Name) pair value to any of the parsers for the Name property type, then the parser transforms the input data pair of (,Last Name, First Name) into modified input data to be stored in an instantiation of a Name property.

If applying a definition at step 310 results in a match to the input data, as tested at step 312, then at step 318 a property instance is created, and the input data field value is stored in a property of the property type associated with the matching sub-definition of the parser definition. For example, referring to FIG. 5A, assume that the input data matches the regular expression 508 for an ADDRESS value. The mapping 510 specifies how to store the data matching each grouping of the regular expression into a component of the ADDRESS property. In response, an instance of an ADDRESS property is created in computer memory and the matching modified input data value is stored in each component of the property instance.

If no match occurs at step 312, then control transfers to step 314 to test whether other parser definitions match the same input data value. FIG. 5B illustrates an example property editing wizard in which multiple parsers have been created for a particular property, and through the loop shown in FIG. 3, each of the multiple parsers can be used in matching input data. If no match occurs to the given parser definition, then any other parser definitions for that property type are matched until either no match occurs, or no other parser definitions are available.

If a grouping is empty, then the component is filled by the default value for that component, if it exists. If no other parser definitions are available, then control transfers from step 314 to step 316, at which point an error is raised or the property is discarded

At step 320, the preceding steps are repeated for all other values and rows in the input data until the process has transformed all the input data into properties in memory.

At step 322, an object of the correct object type is instantiated. For example, the object-property mapping 101 may specify an object type for particular input data, and that type of object is instantiated. The newly created object is associated in memory with the properties that are already in memory. The resulting object is stored in the database in step 324.

Steps in the preceding process may be organized in a pipeline. Using the approaches herein, a user can self-define a database ontology and use automated, machine-based techniques to transform input data according to user-defined parsers and store the transformed data in the database according to the ontology. The approach provides efficient movement of data into a database according to an ontology. The input data has improved intelligibility after transformation because the data is stored in a canonical ontology. Further, the approach is flexible and adaptable, because the user can modify the ontology at any time and is not tied to a fixed ontology. The user also can define multiple parsers to result in semantic matches to input data even when the syntax of the input data is variable.

IV. Example Implementation Hardware

FIG. 6 is a block diagram that illustrates a computer system 600 upon which an embodiment of the invention may be implemented. Computer system 600 includes a bus 602 or other communication mechanism for communicating information, and a processor 604 coupled with bus 602 for processing information. Computer system 600 also includes a main memory 606, such as a random access memory (RAM) or other dynamic storage device, coupled to bus 602 for storing information and instructions to be executed by processor 604. Main memory 606 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 604. Computer system 600 further includes a read only memory (ROM) 608 or other static storage device coupled to bus 602 for storing static information and instructions for processor 604. A storage device 610, such as a magnetic disk or optical disk, is provided and coupled to bus 602 for storing information and instructions.

Computer system 600 may be coupled via bus 602 to a display 612, such as a cathode ray tube (CRT), for displaying information to a computer user. An input device 614, including alphanumeric and other keys, is coupled to bus 602 for communicating information and command selections to processor 604. Another type of user input device is cursor control 616, such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to processor 604 and for controlling cursor movement on display 612. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allows the device to specify positions in a plane.

The invention is related to the use of computer system 600 for implementing the techniques described herein. According to one embodiment of the invention, those techniques are performed by computer system 600 in response to processor 604 executing one or more sequences of one or more instructions contained in main memory 606. Such instructions may be read into main memory 606 from another machine-readable medium, such as storage device 610. Execution of the sequences of instructions contained in main memory 606 causes processor 604 to perform the process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions to implement the invention. Thus, embodiments of the invention are not limited to any specific combination of hardware circuitry and software.

The term “machine-readable medium” as used herein refers to any medium that participates in providing data that causes a machine to operation in a specific fashion. In an embodiment implemented using computer system 600, various machine-readable media are involved, for example, in providing instructions to processor 604 for execution. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media includes, for example, optical or magnetic disks, such as storage device 610. Volatile media includes dynamic memory, such as main memory 606. Transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise bus 602. Transmission media can also take the form of acoustic or light waves, such as those generated during radio wave and infrared data communications. All such media must be tangible to enable the instructions carried by the media to be detected by a physical mechanism that reads the instructions into a machine.

Common forms of machine-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, a CD-ROM, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read.

Various forms of machine-readable media may be involved in carrying one or more sequences of one or more instructions to processor 604 for execution. For example, the instructions may initially be carried on a magnetic disk of a remote computer. The remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem. A modem local to computer system 600 can receive the data on the telephone line and use an infrared transmitter to convert the data to an infrared signal. An infrared detector can receive the data carried in the infrared signal and appropriate circuitry can place the data on bus 602. Bus 602 carries the data to main memory 606, from which processor 604 retrieves and executes the instructions. The instructions received by main memory 606 may optionally be stored on storage device 610 either before or after execution by processor 604.

Computer system 600 also includes a communication interface 618 coupled to bus 602. Communication interface 618 provides a two-way data communication coupling to a network link 620 that is connected to a local network 622. For example, communication interface 618 may be an integrated services digital network (ISDN) card or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, communication interface 618 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, communication interface 618 sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.

Network link 620 typically provides data communication through one or more networks to other data devices. For example, network link 620 may provide a connection through local network 622 to a host computer 624 or to data equipment operated by an Internet Service Provider (ISP) 626. ISP 626 in turn provides data communication services through the worldwide packet data communication network now commonly referred to as the “Internet” 628. Local network 622 and Internet 628 both use electrical, electromagnetic or optical signals that carry digital data streams. The signals through the various networks and the signals on network link 620 and through communication interface 618, which carry the digital data to and from computer system 600, are exemplary forms of carrier waves transporting the information.

Computer system 600 can send messages and receive data, including program code, through the network(s), network link 620 and communication interface 618. In the Internet example, a server 630 might transmit a requested code for an application program through Internet 628, ISP 626, local network 622 and communication interface 618.

The received code may be executed by processor 604 as it is received, and/or stored in storage device 610, or other non-volatile storage for later execution. In this manner, computer system 600 may obtain application code in the form of a carrier wave.

In the foregoing specification, embodiments of the invention have been described with reference to numerous specific details that may vary from implementation to implementation. Thus, the sole and exclusive indicator of what is the invention, and is intended by the applicants to be the invention, is the set of claims that issue from this application, in the specific form in which such claims issue, including any subsequent correction. Any definitions expressly set forth herein for terms contained in such claims shall govern the meaning of such terms as used in the claims. Hence, no limitation, element, property, feature, advantage or attribute that is not expressly recited in a claim should limit the scope of such claim in any way. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. 

What is claimed is:
 1. A non-transitory machine-readable storage medium storing one or more sequences of instructions comprising instructions for generating a graphical user interface, which instructions, when executed by one or more processors, cause: generating an expression pattern field, of the graphical user interface, that is configured to accept user input specifying a transformation expression pattern that specifies how to transform first input data into modified input data; generating parser sub-definition fields, of the graphical user interface, that are configured to accept user input specifying two or more parser sub-definitions, wherein for each parser sub-definition the parser sub-definition fields include: a first field configured to accept user input specifying a portion of the transformation expression pattern; a second field configured to accept user input specifying a component of one of a plurality of object property types of an ontology of a data store; wherein each component is associated with a data type of data; wherein each parser sub-definition, of the two or more parser sub-definitions, specifies how to transform a portion of the first input data into a portion of the modified input data that is to be stored in the component of one of the object property types; storing the transformation expression pattern in association with the two or more parser sub-definitions, wherein the transformation expression pattern, if matched to the first input data, would cause storage of portions of the first input data in components of the object property types that are specified by the two or more parser sub-definitions.
 2. The non-transitory machine-readable storage medium of claim 1, wherein the instructions that cause generating the parser sub-definition fields of the graphical user interface further comprise instructions which, when executed by the one or more processors, cause generating for each parser sub-definition an attribute field that is configured to receive user input specifying an attribute of that parser sub-definition.
 3. The non-transitory machine-readable storage medium of claim 1, wherein the instructions that cause generating the parser sub-definition fields of the graphical user interface further comprise instructions which, when executed by the one or more processors, cause generating for each parser sub-definition a constraint field that is configured to receive user input specifying a constraint on the portion of modified input data that is to be stored in a component of the specified object property type.
 4. The non-transitory machine-readable storage medium of claim 1, wherein the instructions that cause generating the parser sub-definition fields of the graphical user interface further comprise instructions which, when executed by the one or more processors, cause generating for each parser sub-definition a default field that is configured to receive user input specifying a default value to substitute for a missing component of the modified input data.
 5. A method comprising: receiving first input data; accessing an ontology for a data store, wherein the ontology comprises a plurality of object property types; determining whether the first input data matches one or more parser definitions that specify two or more parser sub-definitions, wherein each of the two or more parser sub-definitions specifies how to transform a portion of the first input data into a portion of modified input data that is compatible with a component of one of the object property types of the ontology for the data store; wherein each component is associated with a data type of data; using a matching one of the one or more parser sub-definitions, creating a property instance of the object property type that is associated with the matching one of the one or more parser sub-definitions, and storing the portion of the modified input data in a component of the property instance; wherein the method is performed by one or more computer systems.
 6. The method of claim 5, wherein the one or more parser definitions comprise one or more transformation expressions, wherein each of the transformation expressions comprises one or more syntactic patterns and a property type identifier associated with each of the syntactic patterns, and wherein the method further comprises: determining whether the first input data matches one of the syntactic patterns; using a matching one of the syntactic patterns, creating and storing the modified input data in the property instance of the object property type that is identified by the property type identifier associated with the matching one of the syntactic patterns.
 7. The method of claim 5, comprising: using a transformation expressed in the matching one of the one or more parser definitions to transform the portion of the first input data into the portion of the modified input data that is compatible with a component of said one object property type of the ontology for the data store; storing the portion of the modified input data in a component of the object property type that is associated with the matching one of the one or more parser definitions.
 8. The method of claim 5, wherein the one or more parser definitions are associated with one or more program code modules, wherein each of the program code modules comprises computer program code which when executed causes transforming the first input data into the modified input data.
 9. The method of claim 5, wherein the one or more parser definitions are associated with one or more regular expressions, wherein each of the regular expressions when executed causes transforming the first input data into the modified input data.
 10. A method comprising: receiving first input data; accessing an object-property mapping associated with an ontology for a data store, wherein the ontology comprises a plurality of data object types and a plurality of object property types; based on the object-property mapping, identifying a data object type, of the plurality of data object types, that is associated with input data rows in the first input data, wherein the data object type is mapped to two or more object property types; selecting, from a plurality of parser definitions, one or more parser definitions that match the input data rows; transforming the input data rows into data object instances of the identified data object type by using the one or more parser definitions, wherein each of the one or more parser definitions specifies two or more sub-definitions, wherein each of the two or more sub-definitions specifies how to transform one or more data values from one or more of the input data rows into one or more modified data values that are each compatible with a component of one of the plurality of the object property types of the ontology for the data store; wherein each component is associated with a data type of data; wherein transforming the input data rows into the data object instances further comprises creating a particular data object instance for a particular data row of the input data rows at least in part by performing: reading one or more data values from the particular row; for the particular data object instance: creating a component of an object property type that is associated with a matching one of the two or more sub-definition specified in the one of the one or more parser definitions; storing a particular data value of the one or more data values in the component that is associated with the matching sub-definition; storing the data object instances in the data store; wherein the method is performed by one or more computer systems.
 11. The method of claim 10, comprising: iterating through the plurality of parser definitions in one or more iterations; at each of the one or more iterations, determining whether there is a match between one or more of the input data rows and a parser definition.
 12. A non-transitory machine-readable storage medium storing one or more sequences of instructions comprising instructions which, when executed by one or more processors, cause: receiving first input data; accessing an ontology for a data store, wherein the ontology comprises a plurality of object property types; determining whether the first input data matches one or more parser definitions that specify two or more parser sub-definitions, wherein each of the two or more parser sub-definitions specifies how to transform a portion of the first input data into a portion of modified input data that is compatible with a component of one of the object property types of the ontology for the data store; wherein each component with a data type of data; using a matching one of the one or more parser sub-definitions, creating a property instance of the object property type that is associated with the matching one of the one or more parser sub-definitions, and storing the portion of the modified input data in a component of the property instance.
 13. The non-transitory machine-readable storage medium of claim 12, wherein the one or more parser definitions comprise one or more transformation expressions, wherein each of the transformation expressions comprises one or more syntactic patterns and a property type identifier associated with each of the syntactic patterns, and wherein the one or more sequences of instructions further comprise instructions which, when executed by the one or more processors, cause: determining whether the first input data matches one of the syntactic patterns; using a matching one of the syntactic patterns, creating and storing the modified input data in the property instance of the object property type that is identified by the property type identifier associated with the matching one of the syntactic patterns.
 14. The non-transitory machine-readable storage medium of claim 12, wherein the instructions, when executed by the one or more processors, cause: using a transformation expressed in the matching one of the one or more parser definitions to transform the portion of the first input data into the portion of the modified input data that is compatible with a component of said one object property type of the ontology for the data store; storing the portion of the modified input data in a component of the object property type that is associated with the matching one of the one or more parser sub-definitions.
 15. The non-transitory machine-readable storage medium of claim 12, wherein the one or more parser definitions are associated with one or more program code modules, wherein each of the program code modules comprises computer program code which when executed causes transforming the first input data into the modified input data.
 16. The non-transitory machine-readable storage medium of claim 12, wherein the one or more parser definitions are associated with one or more regular expressions, wherein each of the regular expressions when executed causes transforming the first input data into the modified input data.
 17. A non-transitory machine-readable storage medium storing one or more sequences of instructions comprising instructions which, when executed by one or more processors, cause: receiving first input data; accessing an object-property mapping associated with an ontology for a data store, wherein the ontology comprises a plurality of data object types and a plurality of object property types; based on the object-property mapping, identifying a data object type, of the plurality of data object types, that is associated with input data rows in the first input data, wherein the data object type is mapped to two or more object property types; selecting, from a plurality of parser definitions, one or more parser definitions that match the input data rows; transforming the input data rows into data object instances of the identified data object type by using one or more parser definitions, wherein each of the one or more parser definitions specifies two or more sub-definitions, wherein each of the two or more sub-definitions specifies how to transform one or more data values from one or more of the input data rows into one or more modified data values that are each compatible with a component of one of the plurality of object property types of the ontology for the data store; wherein each component is associated with a data type of data; wherein transforming the input data rows into the data object instances further comprises creating a particular data object instance for a particular data row of the input data rows at least in part by performing: reading one or more data values from the particular row; for the particular data object instance: creating a component of an object property type that is associated with a matching sub-definition specified in the one of the one or more parser definitions; storing a particular data value of the one or more data values in the property component that is associated with the matching sub-definition; storing the data object instances in the data store.
 18. The non-transitory machine-readable storage medium of claim 17, wherein the instructions, when executed by the one or more processors, cause: iterating through the plurality of parser definitions in one or more iterations; at each of the one or more iterations, determining whether there is a match between one or more of the input data rows and a parser definition.
 19. The method of claim 10, wherein the one or more parser definitions specify one or more expression patterns that match the input data rows.
 20. The method of claim 10, wherein at least one of the plurality of data object types is a person.
 21. The method of claim 10, wherein at least one component of at least one of the plurality of the object property types is a zip code.
 22. The non-transitory machine-readable storage medium of claim 17, wherein the one or more parser definitions specify one or more expression patterns that match the input data rows.
 23. The non-transitory machine-readable storage medium of claim 17, wherein at least one of the plurality of data object types is a person.
 24. The non-transitory machine-readable storage medium of claim 17, wherein at least one component of at least one of the plurality of the object property types is a zip code.
 25. A method for generating a graphical user interface, the method comprising: generating an expression pattern field, of the graphical user interface, that is configured to accept user input specifying a transformation expression pattern that specifies how to transform first input data into modified input data; generating parser sub-definition fields, of the graphical user interface, that are configured to accept user input specifying two or more parser sub-definitions, wherein for each parser sub- definition the parser sub-definition fields include: a first field configured to accept user input specifying a portion of the transformation expression pattern; a second field configured to accept user input specifying a component of one of a plurality of object property types of an ontology of a data store; wherein each component is associated with a data type of data; wherein each parser sub-definition, of the two or more parser sub-definitions, specifies how to transform a portion of the first input data into a portion of the modified input data that is to be stored in the component of one of the object property types; storing the transformation expression pattern in association with the two or more parser sub-definitions, wherein the transformation expression pattern, if matched to the first input data, would cause storage of portions of the first input data in components of the object property types that are specified by the two or more parser sub-definitions; wherein the method is performed by one or more computer systems.
 26. The method of claim 25, wherein generating the parser sub-definition fields of the graphical user interface comprises generating for each parser sub-definition an attribute field that is configured to receive user input specifying an attribute of that parser sub-definition.
 27. The method of claim 25, wherein generating the parser sub-definition fields of the graphical user interface comprises generating for each parser sub-definition a constraint field that is configured to receive user input specifying a constraint on the portion of modified input data that is to be stored in a component of the specified object property type.
 28. The method of claim 25, wherein generating the parser sub-definition fields of the graphical user interface comprises generating for each parser sub-definition a default field that is configured to receive user input specifying a default value to substitute for a missing component of the modified input data. 